Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature/update to new main #6

Merged
merged 653 commits into from
Aug 21, 2024
Merged

Feature/update to new main #6

merged 653 commits into from
Aug 21, 2024

Conversation

vertiq-jordan
Copy link

@vertiq-jordan vertiq-jordan commented Aug 21, 2024

Update our main with PX4 main.

Also made a fix to report motor speed as RPM, which is what px4 actually wants.

dagar and others added 30 commits June 26, 2024 17:10
 - px4_msgs::msg::VehicleLandDetected has been added to dds_topics.yaml
 - new parameter EKF2_LOG_VERBOSE to enable (currently enabled by default)
 - force advertise topics immediately (based on EKF2_LOG_VERBOSE and per aid source configuration)
 - logger optionally log all estimator topics at minimal rate
We had a case where someone took off with an experimental
system with 100% RAM usage on the embedded system
without noticing. This lead to problems during flight.

Since we already have a CPU load check it seems natural
to also check the reported RAM usage.
    - libevents in PX4/Firmware (4e3561c): mavlink/libevents@8d5c446
    - libevents current upstream: mavlink/libevents@9474657
    - Changes: mavlink/libevents@8d5c446...9474657

    9474657 2024-06-13 Beat Küng - cmake: add namespaced target & installation include dir
9f2e68d 2024-06-12 Beat Küng - CMakeLists: set CMAKE_CXX_STANDARD if not set
3204e8f 2024-06-12 Beat Küng - parser.h: use std::vector<EventArgumentDefinition>::size_type
eab8144 2024-04-29 Beat Küng - fix parser: avoid signed to unsigned conversion
159f83e 2024-04-29 Beat Küng - cpp: only enable Wall and others for GCC
…nts.txt

- Fixes matplotlib version expression from ">=3.0.*" ro ">=3.0" which is the right syntax

Fixes issue PX4#23329

Co-authored-by: lee wonwoo <[email protected]>
…atus (PX4#23337)

 - track accel clipping count per axis
 - only set bad_acc_clipping fault_status if at least one axis is
   clipping continuously or if all have been clipping at warning level
 - Note: this doesn't impact the clipping projections that boost the
   accel process noise, pause bias estimation, and skip gravity fusion
   on a per sample basis
Internal testing revealed usability issues. Those and some other
problems are fixed.
This fixes an incorrect check of the device paths during instantiation
of the Septentrio driver that caused the driver to start and not print
an error message.
The documentation for `SEP_DUMP_COMM` was quite unclear and users had to
use the user guide to find out what exactly it did. The new
documentation tries to make the purpose clearer.
Heading wasn't working because of an incorrect check during parsing.
Heading offset was configured as radians but should be configured as
degrees on Septentrio receivers. The parameter was already in degrees
but the configuration logic was changing it into radians. Also allow the
entire allowed range of heading offset values for Septentrio receivers.
sfuhrer and others added 21 commits August 16, 2024 13:57
…t is disabled (PX4#23556)

COM_POS_FS_EPH can be set to -1, in which case the actual failure eph is INFINITY.

Signed-off-by: Silvan Fuhrer <[email protected]>
This is to prevent that a large NAV_ACC_RAD leads to very high return altitudes.

Signed-off-by: Silvan Fuhrer <[email protected]>
PX4#23455)

* Update GZBridge to be able to use gazebo airspeed. Add gz quadtailsitter.

* Fix formatting

---------

Co-authored-by: jmackay2 <[email protected]>
improved GCS parameter description

Co-authored-by: Hamish Willee <[email protected]>
Co-authored-by: Silvan Fuhrer <[email protected]>
Ubuntu 22.04 uses make 4.3 which broke the current `make help` target
Reference:
https://stackoverflow.com/a/26339924

Signed-off-by: Beniamino Pozzan <[email protected]>
)

* FeasibilityChecker: only warn when first waypoint is too far, but still accept mission as valid

* feasiblityChecker: make distance to first waypoint check against home position instead of current position, so it is more constant during a flight

* Apply suggestions from code review

Co-authored-by: Silvan Fuhrer <[email protected]>

* feasibilityCheckerTest: update tests to not fail for first waypoint check

* feasibilityChecker: make comment for 1stwaypointcheck event

* Feasibility check unit test: fix comment

Signed-off-by: Silvan Fuhrer <[email protected]>

---------

Signed-off-by: Silvan Fuhrer <[email protected]>
Co-authored-by: Silvan Fuhrer <[email protected]>
@vertiq-jordan vertiq-jordan removed the request for review from vertiq-luca August 21, 2024 14:04
auto formatting on vertiq telem manager
@vertiq-jordan vertiq-jordan merged commit 0359aff into main Aug 21, 2024
1 check failed
@vertiq-jordan vertiq-jordan deleted the feature/update_to_new_main branch August 21, 2024 14:19
@vertiq-jordan vertiq-jordan restored the feature/update_to_new_main branch August 21, 2024 14:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.